Generating and displaying customized avatars in media overlays

ABSTRACT

Among other things, embodiments of the present disclosure improve the functionality of electronic messaging and imaging software and systems by generating and displaying media overlays with avatars of different users. For example, media overlays can be generated by the system and displayed in conjunction with media content (e.g., images and/or video) generated by an image-capturing device (e.g., a digital camera).

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 16/115,259, filed Aug. 28, 2018, which is a continuation of U.S. patent application Ser. No. 15/369,499, filed Dec. 5, 2016, which claims the benefit of priority to U.S. Provisional Patent Application Ser. No. 62/412,115, filed Oct. 24, 2016, the disclosures of each of which are incorporated by reference in their entireties.

BACKGROUND

The popularity of electronic messaging, particularly instant messaging, continues to grow. Users increasingly use “emoji” (which are ideograms and icons) within electronic messages such as texts and emails. Users also increasingly share media content items such as electronic images and videos with each other, reflecting a global demand to communicate more visually. However, conventional emoji and similar graphics that may be used in conjunction with electronic messages, images, and video are typically generic and lacking in diversity: every individual user is represented by the same set of faces, irrespective of appearance, gender or ethnicity. Furthermore, every conversation that uses conventional emoji looks identical, and there is no visual personality or cue to identify the participants or distinguish one interaction from the next. Embodiments of the present disclosure address these and other issues.

BRIEF DESCRIPTION OF THE DRAWINGS

In the drawings, which are not necessarily drawn to scale, like numerals may describe similar components in different views. Like numerals having different letter suffixes may represent different instances of similar components. Some embodiments are illustrated by way of example, and not limitation, in the figures of the accompanying drawings in which:

FIG. 1 is a block diagram showing an example messaging system for exchanging data (e.g., messages and associated content) over a network.

FIG. 2 is block diagram illustrating further details regarding a messaging system, according to exemplary embodiments.

FIG. 3 is a schematic diagram illustrating data which may be stored in the database of the messaging server system, according to various exemplary embodiments.

FIGS. 4A and 4B are flow diagrams of exemplary processes according to various aspects of the disclosure.

FIGS. 5A-5F are screenshots illustrating the steps of the methods described in FIGS. 4A and 4B.

FIG. 6 is a block diagram illustrating a representative software architecture, which may be used in conjunction with various hardware architectures herein described.

FIG. 7 is a block diagram illustrating components of a machine, according to some exemplary embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein.

DETAILED DESCRIPTION

The description that follows includes systems, methods, techniques, instruction sequences, and computing machine program products that embody illustrative embodiments of the disclosure. In the following description, for the purposes of explanation, numerous specific details are set forth in order to provide an understanding of various embodiments of the inventive subject matter. It will be evident, however, to those skilled in the art, that embodiments of the inventive subject matter may be practiced without these specific details. In general, well-known instruction instances, protocols, structures, and techniques are not necessarily shown in detail.

Among other things, embodiments of the present disclosure improve the functionality of electronic messaging and imaging software and systems by generating and displaying media overlays with avatars of different users. For example, media overlays can be generated by the system and displayed in conjunction with media content (e.g., images and/or video) generated by an image-capturing device (e.g., a digital camera).

In some embodiments, media overlays may also be generated that contain avatars of users who exchange electronic communications, such as SMS or MMS texts and emails. Such overlays may be automatically generated based on the history of communications between users, the users' locations, and events the users are engaged in. The appearance of users' avatars in such overlays may likewise be modified based on location and event information. In some embodiments, media overlays may be presented to a user in a gallery or carousel that include customized avatars of the user and the user's friends/contacts.

FIG. 1 is a block diagram showing an example of a messaging system 100 for exchanging data (e.g., messages and associated content) over a network. The messaging system 100 includes multiple client devices 102, each of which hosts a number of applications including a messaging client application 104. Each messaging client application 104 is communicatively coupled to other instances of the messaging client application 104 and a messaging server system 108 via a network 106 (e.g., the Internet). As used herein, the term “client device” may refer to any machine that interfaces to a communications network (such as network 106) to obtain resources from one or more server systems or other client devices. A client device may be, but is not limited to, a mobile phone, desktop computer, laptop, portable digital assistants (PDAs), smart phones, tablets, ultra books, netbooks, laptops, multi-processor systems, microprocessor-based or programmable consumer electronics, game consoles, set-top boxes, or any other communication device that a user may use to access a network.

In the example shown in FIG. 1 , each messaging client application 104 is able to communicate and exchange data with another messaging client application 104 and with the messaging server system 108 via the network 106. The data exchanged between messaging client applications 104, and between a messaging client application 104 and the messaging server system 108, includes functions (e.g., commands to invoke functions) as well as payload data (e.g., text, audio, video or other multimedia data).

The network 106 may include, or operate in conjunction with, an ad hoc network, an intranet, an extranet, a virtual private network (VPN), a local area network (LAN), a wireless LAN (WLAN), a wide area network (WAN), a wireless WAN (WWAN), a metropolitan area network (MAN), the Internet, a portion of the Internet, a portion of the Public Switched Telephone Network (PSTN), a plain old telephone service (POTS) network, a cellular telephone network, a wireless network, a Wi-Fi® network, another type of network, or a combination of two or more such networks. For example, a network or a portion of a network may include a wireless or cellular network and the coupling may be a Code Division Multiple Access (CDMA) connection, a Global System for Mobile communications (GSM) connection, or other type of cellular or wireless coupling. In this example, the coupling may implement any of a variety of types of data transfer technology, such as Single Carrier Radio Transmission Technology (1×RTT), Evolution-Data Optimized (EVDO) technology, General Packet Radio Service (GPRS) technology, Enhanced Data rates for GSM Evolution (EDGE) technology, third Generation Partnership Project (3GPP) including 3G, fourth generation wireless (4G) networks, Universal Mobile Telecommunications System (UMTS), High Speed Packet Access (HSPA), Worldwide Interoperability for Microwave Access (WiMAX), Long Term Evolution (LTE) standard, others defined by various standard setting organizations, other long range protocols, or other data transfer technology.

The messaging server system 108 provides server-side functionality via the network 106 to a particular messaging client application 104. While certain functions of the messaging system 100 are described herein as being performed by either a messaging client application 104 or by the messaging server system 108, it will be appreciated that the location of certain functionality either within the messaging client application 104 or the messaging server system 108 is a design choice. For example, it may be technically preferable to initially deploy certain technology and functionality within the messaging server system 108, but to later migrate this technology and functionality to the messaging client application 104 where a client device 102 has a sufficient processing capacity.

The messaging server system 108 supports various services and operations that are provided to the messaging client application 104. Such operations include transmitting data to, receiving data from, and processing data generated by the messaging client application 104. This data may include, message content, client device information, geolocation information, media annotation and overlays, message content persistence conditions, social network information, and live event information, as examples. Data exchanges within the messaging system 100 are invoked and controlled through functions available via user interfaces (UIs) of the messaging client application 104.

Turning now specifically to the messaging server system 108, an Application Program Interface (API) server 110 is coupled to, and provides a programmatic interface to, an application server 112. The application server 112 is communicatively coupled to a database server 118, which facilitates access to a database 120 in which is stored data associated with messages processed by the application server 112.

Dealing specifically with the Application Program Interface (API) server 110, this server receives and transmits message data (e.g., commands and message payloads) between the client device 102 and the application server 112. Specifically, the Application Program Interface (API) server 110 provides a set of interfaces (e.g., routines and protocols) that can be called or queried by the messaging client application 104 in order to invoke functionality of the application server 112. The Application Program Interface (API) server 110 exposes various functions supported by the application server 112, including account registration, login functionality, the sending of messages, via the application server 112, from a particular messaging client application 104 to another messaging client application 104, the sending of electronic media files (e.g., electronic images and/or video) from a messaging client application 104 to the messaging server application 114, and for possible access by another messaging client application 104, the setting of a collection of media data (e.g., story), the retrieval of a list of friends of a user of a client device 102, the retrieval of such collections, the retrieval of messages and content, the adding and deletion of friends to a social graph, the location of friends within a social graph, opening and application event (e.g., relating to the messaging client application 104).

The application server 112 hosts a number of applications and subsystems, including a messaging server application 114, an image processing system 116 and a social network system 122. The messaging server application 114 implements a number of message processing technologies and functions, particularly related to the aggregation and other processing of content (e.g., textual and multimedia content including images and video clips) included in messages received from multiple instances of the messaging client application 104. As will be described in further detail, the text and media content from multiple sources may be aggregated into collections of content (e.g., called stories or galleries). These collections are then made available, by the messaging server application 114, to the messaging client application 104. Other processor and memory intensive processing of data may also be performed server-side by the messaging server application 114, in view of the hardware requirements for such processing.

The application server 112 also includes an image processing system 116 that is dedicated to performing various image processing operations, typically with respect to electronic images and/or video received within the payload of a message at the messaging server application 114.

The social network system 122 supports various social networking functions services, and makes these functions and services available to the messaging server application 114. To this end, the social network system 122 maintains and accesses an entity graph 304 within the database 120. Examples of functions and services supported by the social network system 122 include the identification of other users of the messaging system 100 with which a particular user has relationships or is “following”, and also the identification of other entities and interests of a particular user.

The application server 112 is communicatively coupled to a database server 118, which facilitates access to a database 120 in which is stored data associated with messages processed by the messaging server application 114.

Some embodiments may include one or more wearable devices, such as a pendant with an integrated camera that is integrated with, in communication with, or coupled to, a client device 102. Any desired wearable device may be used in conjunction with the embodiments of the present disclosure, such as a watch, eyeglasses, goggles, a headset, a wristband, earbuds, clothing (such as a hat or jacket with integrated electronics), a clip-on electronic device, and/or any other wearable devices.

FIG. 2 is block diagram illustrating further details regarding the messaging system 100, according to exemplary embodiments. Specifically, the messaging system 100 is shown to comprise the messaging client application 104 and the application server 112, which in turn embody a number of some subsystems, namely an ephemeral timer system 202, a collection management system 204 and an annotation system 206.

The ephemeral timer system 202 is responsible for enforcing the temporary access to content permitted by the messaging client application 104 and the messaging server application 114. To this end, the ephemeral timer system 202 incorporates a number of timers that, based on duration and display parameters associated with a message, or collection of messages (e.g., a SNAPCHAT story), selectively display and enable access to messages and associated content via the messaging client application 104.

The collection management system 204 is responsible for managing collections of media (e.g., collections of text, image video and audio data). In some examples, a collection of content (e.g., messages, including images, video, text and audio) may be organized into an “event gallery” or an “event story.” Such a collection may be made available for a specified time period, such as the duration of an event to which the content relates. For example, content relating to a music concert may be made available as a “story” for the duration of that music concert. The collection management system 204 may also be responsible for publishing an icon that provides notification of the existence of a particular collection to the user interface of the messaging client application 104.

The collection management system 204 furthermore includes a curation interface 208 that allows a collection manager to manage and curate a particular collection of content. For example, the curation interface 208 enables an event organizer to curate a collection of content relating to a specific event (e.g., delete inappropriate content or redundant messages).

Additionally, the collection management system 204 employs machine vision (or image recognition technology) and content rules to automatically curate a content collection. In certain embodiments, compensation may be paid to a user for inclusion of user generated content into a collection. In such cases, the curation interface 208 operates to automatically make payments to such users for the use of their content.

The annotation system 206 provides various functions that enable a user to annotate or otherwise modify or edit media content associated with a message. For example, the annotation system 206 provides functions related to the generation and publishing of media overlays for messages processed by the messaging system 100. The annotation system 206 operatively supplies a media overlay (e.g., a SNAPCHAT filter) to the messaging client application 104 based on a geolocation of the client device 102. In another example, the annotation system 206 operatively supplies a media overlay to the messaging client application 104 based on other information, such as, social network information of the user of the client device 102. A media overlay may include audio and visual content and visual effects. Examples of audio and visual content include pictures, texts, logos, animations, and sound effects. An example of a visual effect includes color overlaying. The audio and visual content or the visual effects can be applied to a media content item (e.g., an image or video) at the client device 102. For example, the media overlay including text that can be overlaid on top of a photograph/electronic image generated by the client device 102. In another example, the media overlay includes an identification of a location overlay (e.g., Venice beach), a name of a live event, or a name of a merchant overlay (e.g., Beach Coffee House). In another example, the annotation system 206 uses the geolocation of the client device 102 to identify a media overlay that includes the name of a merchant at the geolocation of the client device 102. The media overlay may include other indicia associated with the merchant. The media overlays may be stored in the database 120 and accessed through the database server 118.

In some exemplary embodiments, as discussed in more detail below, embodiments of the present disclosure may generate, display, and apply media overlays to media content items where the media overlays include customized avatars of one or more users. For example, the avatar may represent the user of a computing device performing functionality of the embodiments of the present disclosure. Additionally or alternatively, the media overlay can include an avatar representing one or more other users, such as friends of the user in the user's contact list, as well as one or more users with whom the user of a computing device exchanges electronic communications such as text messages, emails, and media content.

In one exemplary embodiment, the annotation system 206 provides a user-based publication platform that enables users to select a geolocation on a map, and upload content associated with the selected geolocation. The user may also specify circumstances under which a particular media overlay should be offered to other users. The annotation system 206 generates a media overlay that includes the uploaded content and associates the uploaded content with the selected geolocation.

In another exemplary embodiment, the annotation system 206 provides a merchant-based publication platform that enables merchants to select a particular media overlay associated with a geolocation via a bidding process. For example, the annotation system 206 associates the media overlay of a highest bidding merchant with a corresponding geolocation for a predefined amount of time

FIG. 3 is a schematic diagram 300 illustrating data 300 that is stored in the database 120 of the messaging server system 108, according to certain exemplary embodiments. While the content of the database 120 is shown to comprise a number of tables, the data could be stored in other types of data structures (e.g., as an object-oriented database).

The database 120 includes message data stored within a message table 314. The entity table 302 stores entity data, including an entity graph 304. Entities for which records are maintained within the entity table 302 may include individuals, corporate entities, organizations, objects, places, events etc. Regardless of type, any entity regarding which the messaging server system 108 stores data may be a recognized entity. Each entity is provided with a unique identifier, as well as an entity type identifier (not shown).

The entity graph 304 furthermore stores information regarding relationships and associations between entities. Such relationships may be social, professional (e.g., work at a common corporation or organization) interested-based or activity-based, merely for example.

The database 120 also stores annotation data, in the example form of filters, in an annotation table 312. Filters for which data is stored within the annotation table 312 are associated with and applied to videos (for which data is stored in a video table 310) and/or images (for which data is stored in an image table 308). Filters, in one example, are overlays that are displayed as overlaid on an image or video during presentation to a recipient user. Filters may be of varies types, including a user-selected filters from a gallery of filters presented to a sending user by the messaging client application 104 when the sending user is composing a message. Other types of filters include geolocation filters (also known as Geofilters) which may be presented to a sending user based on geographic location. For example, geolocation filters specific to a neighborhood or special location may be presented within a user interface by the messaging client application 104, based on geolocation information determined by a GPS unit of the client device 102. Another type of filter is a data filter, which may be selectively presented to a sending user by the messaging client application 104, based on other inputs or information gathered by the client device 102 during the message creation process. Example of data filters include current temperature at a specific location, a current speed at which a sending user is traveling, battery life for a client device 102 or the current time.

Other annotation data that may be stored within the image table 308 is so-called “Lens” data. A “Lens” may be a real-time special effect and sound that may be added to an image or a video.

As mentioned above, the video table 310 stores video data which, in one embodiment, is associated with messages for which records are maintained within the message table 314. Similarly, the image table 308 stores image data associated with messages for which message data is stored in the entity table 302. The entity table 302 may associate various annotations from the annotation table 312 with various images and videos stored in the image table 308 and the video table 310.

A story table 306 stores data regarding collections of messages and associated image, video or audio data, which are compiled into a collection (e.g., a SNAPCHAT story or a gallery). The creation of a particular collection may be initiated by a particular user (e.g., each user for which a record is maintained in the entity table 302). A user may create a “personal story” in the form of a collection of content that has been created and sent/broadcast by that user. To this end, the user interface of the messaging client application 104 may include an icon that is user selectable to enable a sending user to add specific content to his or her personal story.

A collection may also constitute a “live story,” which is a collection of content from multiple users that is created manually, automatically or using a combination of manual and automatic techniques. For example, a “live story” may constitute a curated stream of user-submitted content from varies locations and events. Users, whose client devices have location services enabled and are at a common location event at a particular time may, for example, be presented with an option, via a user interface of the messaging client application 104, to contribute content to a particular live story. The live story may be identified to the user by the messaging client application 104, based on his or her location. The end result is a “live story” told from a community perspective.

A further type of content collection is known as a “location story,” which enables a user whose client device 102 is located within a specific geographic location (e.g., on a college or university campus) to contribute to a particular collection. In some embodiments, a contribution to a location story may require a second degree of authentication to verify that the end user belongs to a specific organization or other entity (e.g., is a student on the university campus).

Embodiments of the present disclosure may generate and present customized images for use within electronic messages/communications such as short message service (SMS) or multimedia message service (MMS) texts and emails. The customized images may also be utilized in conjunction with the SNAPCHAT stories, SNAPCHAT filters, and ephemeral messaging functionality discussed herein.

FIG. 4A depicts an exemplary process according to various aspects of the present disclosure. In this example, method 400 includes receiving a media content item (402), retrieving avatar characteristics for a user (404), generating a media overlay (406), displaying the media overlay with the media content item (408), and applying the media overlay to the media content item (410). Method 400 further includes storing a history of overlaid media content items (412), retrieving the history of media content items (414), and displaying the history of overlaid media content items (416).

FIG. 4B depicts another exemplary process 420 that includes retrieving communication data regarding communications between one or more users (420), determining a relationship between the users based on the communication data (424), generating avatar characteristics based on the relationship (426), generating a media overlay containing avatars representing the users based on the avatar characteristics (428), displaying the media overlay with a media content item on a display (430), and transmitting an electronic communication containing the media overlay (432). Method 420 further includes receiving an electronic communication containing a media overlay (434), generating an event story based on communications between users (436), and providing temporary access to the event story (438). The steps of method 400 and 420 may be performed in whole or in part, may be performed in conjunction each other as well as with some or all of the steps in other methods, and may be performed by any number of different systems, such as the systems described in FIGS. 1 and/or 7 .

A variety of media content items may be received (402) from a variety of sources. In this context, a “media content item” may include any type of electronic media in any format. For example, a media content item may include an image in JPG format, an image in PNG format, a video in FLV format, a video in AVI format, etc. In some exemplary embodiments, a media content item is captured using an image capture device or component (such as a digital camera) coupled to, or in communication with, a system performing the functionality of method 400. In the exemplary system 700 depicted in FIG. 7 may include a digital camera as one of input components 728. Additionally or alternatively, the media content item may be received from another system or device. In FIG. 1 , for example, a client device 102 performing the functionality of method 400 may receive a media content item from another client device 102 or other system via network 106.

In method 400, the system retrieves avatar characteristics (404) for a user. In some cases, the user for whom avatar characteristics are retrieved may be a user of the system performing the steps of method 400 (such as client device 102 in FIG. 1 ). Additionally or alternatively, the system may retrieve avatar characteristics for a user of another device, a user listed in the contact list of the user of the system, a user of a social network identified by the user of the system, or any other individual. In one exemplary embodiment, the system (e.g., client device 102 in FIG. 1 ) transmits a request to a server (e.g., application server 112) for a media overlay that includes the avatar characteristics for the user. The server may then transmit the media overlay that includes the avatar of the user to the system. In this manner, the system may distribute the creation/generation of some or all of the media overlay with other connected systems and devices.

As used herein, an “avatar” of a user is any visual representation of user. The avatar of a user may be based on characteristics derived from images of the user in conjunction with the avatar characteristics identified from the user's relationships with other users. Alternatively or additionally, the user may select and customize characteristics of the user's avatar via the user's computing device. Such avatar characteristics may include, for example, the user's bodily features (e.g., muscular, thin, etc.), facial features, clothing and accessories, text displayed in conjunction with the avatar, and images displayed in conjunction with the avatar. As discussed in more detail below (with reference to method 420), the system may also generate (426) avatar characteristics for one or more users based on various factors. The avatar characteristics may be retrieved (404) from a variety of sources, such as the local memory of a device performing the steps of method 400 (e.g., client device 102 in FIG. 1 ) as well as from other systems and devices, such as a database or server.

The system generates a media overlay (406) based on the retrieved avatar characteristics to generate an overlay that includes the avatar of one or more users and displays (408) the media overlay in conjunction with a media content item. The overlay may include static (i.e., non-moving) avatars as well as dynamic (i.e., moving) avatars. In some embodiments, application of the overlay (410) may change the format of the image. For example, where the media content item is in a static image format such a JPG, and where the media overlay includes a dynamic component, such as an animated GIF, the system may convert the media content item to an animated GIF to apply the media overlay to the media content item.

The system may also generate and modify other features of the media overlay as part of generating the overlay, such as starting with a template media overlay and modifying the setting, colors, text, avatars, and other features displayed within the media overlay. Among other things, this allows embodiments of the present disclosure to use some standard template features in a media overlay (and thus do not need to recreate each media overlay from scratch) while also allowing the system to customize media overlays to provide a unique graphical experience to each user.

In some embodiments, the system may provide a user with access to a media overlay for a predetermined time period. In some embodiments, media overlays may be received from another system or device (e.g., by client device 102 from application server 112 in FIG. 1 ) and made available for a limited time. Among other things, this helps provide users with new material and encourages them to check the gallery/carousel of media overlays for new content.

In some embodiments, the gallery/carousel of media overlays may include one or more dedicated slots for avatar-based media overlays. Some filters/media overlays might appear in a particular week for as little as 1 minute, giving users who had the luck to find the media overlay a special opportunity to use the media overlay as well as a reason to “tune into” the gallery/carousel throughout the day to see what's new. Among other things, the customized media overlays/filters of the present disclosure help introduce personalization to the media overlays for different users, an opportunity for surprise and serendipity in applying the media overlay to a media content item, the ability to add character to a media content item beyond its original content, and encourage users to check out the gallery/carousel of media overlays to view new content.

Accordingly, display of the media overlay (408) may include presenting a plurality of media overlays on the display screen of a computing device and receiving a selection of one or more media overlays from the plurality of media overlays to display in conjunction with the media content item. The user may then add, remove, and/or modify the displayed media overlays before applying the media overlay(s) to the content item.

In some embodiments, a first media overlay may be redundant or otherwise incompatible with a second media overlay in a selection of media overlays in a gallery/carousel. In such embodiments, the system may receive (e.g., via an input device of a user interface) selection of a first overlay by a user and, in response to the selection of the first media overlay, remove (or disable selection of by, for example, graying out the selection) a second media overlay from the plurality of media overlays presented to the user.

The system may generate the media overlay based on information in addition to, or other than, the avatar characteristics. For example, the media overlay may be generated based on location information for the system (e.g., received from a location sensor coupled to the device performing the steps of method 400), the time of day, the date, an event (such as a holiday or a birthday of the user), and other information. Time and date information can be determined based on time and time zone information from a clock coupled to the system. In FIG. 5E for example, the upper-left media overlay may be displayed in the morning relative to the system on which it is displayed, while the media overlay in the lower right can be displayed in the evening based on the system's time. Likewise, the “Happy Friday” or similar media overlay in FIG. 5F can be generated based on the day of the week as determined from the system's clock.

Embodiments of the present disclosure can also generate a media overlay based on information retrieved/received from one or more sensors coupled to, or in communication with, the system, such as any of the sensor components 730, 734, 736, 738 in system 700 depicted in FIG. 7 . Accordingly, the media overlay may thus be generated based on data from a temperature sensor, velocity sensor, acceleration sensor, altitude sensor, and/or any other sensor information.

Embodiments of the present disclosure may generate any desired content in conjunction with generating (406) the media overlay, including images, video, text, visual effects, etc. In some embodiments, the generation of text and other content may be generated based on identifying a location for the system (e.g., based on location information from a location sensor coupled to the system), identifying a language associated with the system's location, and generating text for the media overlay in the identified language.

In some embodiments the actual time for the system can be displayed as part of the media overlay, such as is shown on the clock around the neck of the avatar in the lower-left media overlay in FIG. 5E. Media overlays can also be generated based on information stored in the user's calendar on the system, such as birthday information (e.g., a “happy birthday” overlay) as well as scheduling information that could be used to determine when the user leaves work, as shown in the upper-right media overlay in FIG. 5E. Location information for the system in conjunction with date and time information may be used to generate media overlays based on holidays in the location where the system is present, such as the “Happy Halloween” media overlay in FIG. 5F

The media overlay can be displayed (408) in conjunction with the media content item on the display screen of a computing device to allow a user to determine if he/she wishes to apply the overlay to the content item, to select from among a plurality of media overlays, as well as to allow the user to modify parameters of the media overlay. For example, a user may be presented the media overlays depicted in FIGS. 5E and 5F in a carousel or gallery to allow the user to see how the overlay will affect the media content item. The user may also be given an interface to modify the color and/or size of features of the media overlay, as well as to edit text in the overlay. In the four media overlays in FIG. 5E, for example, the user may be given an interface to change the text and/or the font/colors of the text prior to application of the overlay to the media content item. In some embodiments, editing of a media overlay or media content item can be performed by a user after the media overlay is applied to the media content item. The user may provide selections (e.g., via the input device of a user interface on the user's computing device) to edit and/or apply (410) the media overlay to the media content item.

As described above, a collection of content, including media content items with applied media overlays may be organized into an “event gallery” or an “event story” and such collections may be made available for a predetermined time period, such as the duration of an event to which the content relates. The system may store (412) a history of media content items with applied media overlays in the memory of the system, a database in communication with the system, and/or another system or device in communication with the system performing the functionality of method 400. The system may retrieve (414) and display (416) some or all of the media content items in such a history as well.

A history of media content items may be stored in any desired format and in any desired manner. In one exemplary embodiment, the media content items store an identifier for the media overlay and an identifier for the user's avatar, rather than a copy of the rendered media content item with the media overlay applied. Upon retrieval (414) the system looks up the media overlay and avatar information and generates the combined media content item/media overlay combination on demand. Among other things, this helps save memory on the user's device as well as on servers and databases that may store the information.

In some embodiments, the avatar of a user may include a version number. If the user or system modifies the user's avatar after a media content item/media overlay combination is saved to a history, the system may use the previous (i.e., originally saved) version of the user's avatar in any rendered media content based on the stored content. In other embodiments, the system may render the filter/media overlay using the current version of the user's avatar.

In the exemplary method 420 shown in FIG. 4B, Embodiments of the present disclosure can retrieve (422) a variety of communication data from a variety of sources. For example, communication data may be retrieved from the memory of a computing device (such as client computing device 102 in FIG. 1 ) performing some or all of the functionality of method 420. Alternately or additionally, communication data may be retrieved from another computing device (e.g., over a network). Communication data may include a history of electronic communications (such as emails, text messages, and the like) between a plurality of users. For example, consider two users, a first user and a second user, who exchange a series of text messages with each other using their respective mobile computing devices (e.g., client computing devices 102 in FIG. 1 ). The computing device of the first user may be adapted to store the messages in its memory for later retrieval, or to request the messages (or information regarding them) from another source (such as application server 112 in FIG. 1 ).

The communication data may include meta data associated with one or more communications, such as the size of the communication, the date/time it was sent, one or more languages used in the communication, identifiers for the sender and/or recipient(s), information regarding the computing devices (e.g. the mobile devices of the sender or recipient or a messaging server) involved in transmitting or receiving the communication, and other information. In the case of identification information, any such identifier may be used, such as the user's full name or a username associated with the user. The user identifier may also be an identifier associated with the user's computing device, such as a Unique Device Identifier (UDID) or Identifier for Advertising (IDFA). The communication data may also include text, images, video, and other content within a communication. For example, the communication data may include terms used by users within one or more communications to address each other, such as “hi mom,” “hey buddy,” “how's my favorite nephew,” and the like. Such terms (and other communication data) may be used to help identify a relationship between users based on their communications with each other as discussed below.

The system may request authorization from a user to analyze communication data associated with the user's communications. The authorization request may be presented to the user via the user's computing device and may allow the user to select the types of communication data the system may analyze as well as allowing the user to entirely disable the system from analyzing the user's communication data altogether. In cases where the user grants the system access to analyze the user's communication data, the system can analyze the communication data to automatically determine (424) a relationship between the user and other users with whom the user communicates.

Embodiments of the present disclosure can identify any number of different relationships between any number of users. Examples of such relationships may include family relationships, friendships, or romantic relationships, as well as others. Embodiments of the disclosure may also identify other aspects of relationships between users, such as whether the users are work colleagues, classmates, roommates, and/or acquaintances. Analysis of communication data to identify relationships between users may also be supplemented with other information, such as data retrieved from social networking sites, as well as direct input from the user providing information on his/her relationships with various users.

Based on the relationship between different users, the system can generate characteristics for avatars (426) that represent the different users and use such avatar characteristics to generate media overlays (428) containing the avatars of the users. Embodiments of the present disclosure may generate (428) images within media overlays containing any number of avatars. For example, an image containing a single avatar may be generated in some cases, while an image containing multiple user avatars may be generated in other cases. FIGS. 5A-5E illustrate exemplary images that include a first avatar representing a first user and a second avatar representing a second user according to various aspects of the disclosure. Such images may be displayed (430) within a media overlay on the display screen of one or more computing devices. Media overlays generated by embodiments of the present disclosure may include any number of user avatars in a variety of forms. For example, FIG. 5A depicts an avatar of a first user with the avatar of a second user on his shirt.

In some embodiments, besides using images containing avatars within media overlays, such images may be used in conjunction with displaying the avatars within a video game. In some cases, the images may be displayed in a single-person game (e.g., played alone by a first user on the first user's computing device) or in a multi-player game (e.g., the game is accessed by the computing device of a first user and the computing device of a second user) played over a network or other connection. During the game, various events may occur and the avatars of one or more users may be modified as a result. For example, an avatar who experiences an injury may be depicted with a black eye, while an avatar who finds an item in the game (e.g., a sword) can be modified to show the avatar carrying the item. In this manner, embodiments of the disclosure allow users to have their own customized avatars (which may be based on their own likenesses) appear in video games as well as in other contexts, such as text messages or other electronic communications.

Generation of the images containing user avatars may be based on an event. The event may affect one user (such as the user's birthday) or be common to multiple users. For example, referring to FIG. 5B, an image depicting avatars of two users is generated based on a day of the week.

Generation of the images containing user avatars may be based on the locations of different users. For example, embodiments of the present disclosure may retrieve location information from the computing devices of two different users. In embodiments where a client computing device (such as client device 102) is performing the image/media overlay generation, location information for the device can be retrieved from the device's global positioning system and location information for the device of another can be requested over a network.

The avatars of different users in different locations can be generated to reflect their respective locations. For example, the avatar of a first user whose mobile computing device indicates is in the tropics could be depicted standing in a bathing suit on a beach, while the avatar of a second user whose mobile device indicates is in an area with snow could be depicted wearing a jacket and shivering. Accordingly, the location information from a device associated with a user can be combined with information regarding the location and/or an event occurring at the location to generate the avatar and/or image. Such location-based information may include weather information, time of day, local customs (such as language and/or dress), and other information.

In some cases, the system can identify that two or more users are in a common location. In this context, a “common location” may be identified as being within any predetermined boundary, such as within the same building, the same city, the same two-block radius, the same state, etc. In such cases, the image in the media overlay can be generated to depict the avatars of multiple users based on the common location. As described above, the image containing multiple avatars may be generated based on information regarding the location as well as identifying an event taking place at the common location. Such events may include, for example, a sporting event, a business meeting, an educational event, a pre-arranged meeting between the user and another person (such as a lunch meeting), and other events.

In one exemplary embodiment, referring to FIG. 5C, the system identifies that a first user and second user are both participating in a race, and that the first user finished the race ahead of the second user. The system then automatically generates a media overlay containing the image in FIG. 5C and presents the media overlay to the first user and/or second user via their mobile computing devices for application with a media content item, such as an image or video of the two users racing. In this example, the details of the event (i.e., race in this case) can be identified by the system based on information from a combination of different sources, such as location information from each user's mobile computing device, information about the race occurring collected from a website hosted by the race's sponsor based on a web search using the identified location, posts by the first and second user to a social media website, and a history of electronic communications between the first and second user where the second user congratulates the first user on winning and the first user consoling the second user. In this manner, the system can utilize a combination of publically-available information and information the system is authorized by the user to access (such as the content of the user's communications) to automatically generate images and media overlays including the user's avatar and/or the avatars of other users.

In some embodiments, the system may modify various features of an avatar, as well as features of an image containing an avatar, based on location information and/or event information. In FIG. 5B, for example, a similar image could be generated for other days of the week where the setting or background of the image displaying the name of the day of the week (e.g., Wednesday vs. Tuesday) can be modified. Likewise, either avatar can be modified based on various information. For example, referring now to FIG. 5D, the system may identify an event taking place at a common location (a cupcake festival in this example) and generate an image of the first user standing next to the second user, where the second user's body is depicted as a cupcake. As above, the image can be generated based on content of communications between the users, such as based on a comment by the second user in a text message to the first user that “I ate so many cupcakes, I feel like one.”

The system can modify avatars and images based on identified events and locations in any suitable manner. For example, avatars of users attending the same sporting event could be depicted in an image wearing the jersey of one of the teams playing at the event. Users attending a paintball event together could result in an image being generated showing avatars of the users holding paintguns and covered in paint. Users attending a mud obstacle race could result in an image being generated showing avatars of the users covered in mud. Furthermore, information from users' electronic communications between each other and/or social network posts can be used to identify an event attended by the user and use such information to generate avatar attributes and images.

In some exemplary embodiments, the system can identify users at a common location, generate images containing the avatars of such users, and initiate (automatically or in response to user activation) the transmission of electronic communications to such users. For example, if a first user and second user attend an event (such as a baseball game at a stadium) together, the system (e.g., via the first user's mobile computing device) may (e.g., automatically with the first user's authorization or in response to the first user's instruction) search for other users in the contact list of the first user's mobile device who are also at the stadium. In response to identifying a third user, the system may then generate an image containing avatars representing the first, second, and third users (e.g., all wearing team jerseys) and transmit an electronic message/communication containing the image (e.g., a part of a media overlay) to a mobile computing device carried by the third user (e.g., in a text message). Among other things, this can help users quickly identify and reach out to people they know at various events and locations.

Embodiments of the present disclosure may transmit (432) and/or receive (434) electronic communications containing images with avatars, including within media overlays.

Any form of electronic communication may be utilized by embodiments of the present disclosure, such as SMS texts, MMS texts, emails, and other communications. Images included in such communications may be provided as attachments, displayed inline in the message, within media overlays, or conveyed in any other suitable manner.

In some embodiments, the system may generate a plurality of images containing one or more avatars and allow a user of the system to select which image(s) he/she wishes to include in an electronic communication and/or in a media overlay. In some embodiments, the generation of such images may be based on the content of communications sent or received by the system, as well as on other communication data as discussed above. In one particular embodiment, a computing device operated by a first user receives (434) an electronic communication from the computing device of a second user, where the communication contains an image that includes avatars representing the first and second user. In this example, the computing device of the first user is adapted to utilize the received image in generating (as in step 406 from FIG. 4A) a media overlay.

As described in more detail above, embodiments of the disclosure may generate an event story or event gallery (436) based on a collection or series of electronic communications (e.g., containing media content items with media overlays applied) between users and provide temporary access to the event story or gallery (438). Any collection of such communications may be selected based on any criteria, and one or more users may be granted access to an event story or gallery for any desired predetermined period of time. Likewise, the system may grant access to images generated by the system or received from other system for a predetermined period of time as described above. Such images may also be presented in conjunction with a media overlay (e.g., a SNAPCHAT filter).

Software Architecture

FIG. 6 is a block diagram illustrating an exemplary software architecture 606, which may be used in conjunction with various hardware architectures herein described. FIG. 6 is a non-limiting example of a software architecture and it will be appreciated that many other architectures may be implemented to facilitate the functionality described herein. The software architecture 606 may execute on hardware such as machine 700 of FIG. 7 that includes, among other things, processors 704, memory 714, and I/O components 718. A representative hardware layer 652 is illustrated and can represent, for example, the machine 700 of FIG. 7 . The representative hardware layer 652 includes a processing unit 654 having associated executable instructions 604. Executable instructions 604 represent the executable instructions of the software architecture 606, including implementation of the methods, components and so forth described herein. The hardware layer 652 also includes memory and/or storage modules memory/storage 656, which also have executable instructions 604. The hardware layer 652 may also comprise other hardware 658.

As used herein, the term “component” may refer to a device, physical entity or logic having boundaries defined by function or subroutine calls, branch points, application program interfaces (APIs), and/or other technologies that provide for the partitioning or modularization of particular processing or control functions. Components may be combined via their interfaces with other components to carry out a machine process. A component may be a packaged functional hardware unit designed for use with other components and a part of a program that usually performs a particular function of related functions.

Components may constitute either software components (e.g., code embodied on a machine-readable medium) or hardware components. A “hardware component” is a tangible unit capable of performing certain operations and may be configured or arranged in a certain physical manner. In various exemplary embodiments, one or more computer systems (e.g., a standalone computer system, a client computer system, or a server computer system) or one or more hardware components of a computer system (e.g., a processor or a group of processors) may be configured by software (e.g., an application or application portion) as a hardware component that operates to perform certain operations as described herein. A hardware component may also be implemented mechanically, electronically, or any suitable combination thereof. For example, a hardware component may include dedicated circuitry or logic that is permanently configured to perform certain operations.

A hardware component may be a special-purpose processor, such as a Field-Programmable Gate Array (FPGA) or an Application Specific Integrated Circuit (ASIC). A hardware component may also include programmable logic or circuitry that is temporarily configured by software to perform certain operations. For example, a hardware component may include software executed by a general-purpose processor or other programmable processor. Once configured by such software, hardware components become specific machines (or specific components of a machine) uniquely tailored to perform the configured functions and are no longer general-purpose processors. It will be appreciated that the decision to implement a hardware component mechanically, in dedicated and permanently configured circuitry, or in temporarily configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

A processor may be, or in include, any circuit or virtual circuit (a physical circuit emulated by logic executing on an actual processor) that manipulates data values according to control signals (e.g., “commands”, “op codes”, “machine code”, etc.) and which produces corresponding output signals that are applied to operate a machine. A processor may, for example, be a Central Processing Unit (CPU), a Reduced Instruction Set Computing (RISC) processor, a Complex Instruction Set Computing (CISC) processor, a Graphics Processing Unit (GPU), a Digital Signal Processor (DSP), an Application Specific Integrated Circuit (ASIC), a Radio-Frequency Integrated Circuit (RFIC) or any combination thereof. A processor may further be a multi-core processor having two or more independent processors (sometimes referred to as “cores”) that may execute instructions contemporaneously.

Accordingly, the phrase “hardware component” (or “hardware-implemented component”) should be understood to encompass a tangible entity, be that an entity that is physically constructed, permanently configured (e.g., hardwired), or temporarily configured (e.g., programmed) to operate in a certain manner or to perform certain operations described herein. Considering embodiments in which hardware components are temporarily configured (e.g., programmed), each of the hardware components need not be configured or instantiated at any one instance in time. For example, where a hardware component comprises a general-purpose processor configured by software to become a special-purpose processor, the general-purpose processor may be configured as respectively different special-purpose processors (e.g., comprising different hardware components) at different times. Software accordingly configures a particular processor or processors, for example, to constitute a particular hardware component at one instance of time and to constitute a different hardware component at a different instance of time. Hardware components can provide information to, and receive information from, other hardware components. Accordingly, the described hardware components may be regarded as being communicatively coupled. Where multiple hardware components exist contemporaneously, communications may be achieved through signal transmission (e.g., over appropriate circuits and buses) between or among two or more of the hardware components. In embodiments in which multiple hardware components are configured or instantiated at different times, communications between such hardware components may be achieved, for example, through the storage and retrieval of information in memory structures to which the multiple hardware components have access.

For example, one hardware component may perform an operation and store the output of that operation in a memory device to which it is communicatively coupled. A further hardware component may then, at a later time, access the memory device to retrieve and process the stored output. Hardware components may also initiate communications with input or output devices, and can operate on a resource (e.g., a collection of information). The various operations of example methods described herein may be performed, at least partially, by one or more processors that are temporarily configured (e.g., by software) or permanently configured to perform the relevant operations. Whether temporarily or permanently configured, such processors may constitute processor-implemented components that operate to perform one or more operations or functions described herein. As used herein, “processor-implemented component” refers to a hardware component implemented using one or more processors. Similarly, the methods described herein may be at least partially processor-implemented, with a particular processor or processors being an example of hardware. For example, at least some of the operations of a method may be performed by one or more processors or processor-implemented components.

Moreover, the one or more processors may also operate to support performance of the relevant operations in a “cloud computing” environment or as a “software as a service” (SaaS). For example, at least some of the operations may be performed by a group of computers (as examples of machines including processors), with these operations being accessible via a network (e.g., the Internet) and via one or more appropriate interfaces (e.g., an Application Program Interface (API)). The performance of certain of the operations may be distributed among the processors, not only residing within a single machine, but deployed across a number of machines. In some exemplary embodiments, the processors or processor-implemented components may be located in a single geographic location (e.g., within a home environment, an office environment, or a server farm). In other exemplary embodiments, the processors or processor-implemented components may be distributed across a number of geographic locations.

In the exemplary architecture of FIG. 6 , the software architecture 606 may be conceptualized as a stack of layers where each layer provides particular functionality. For example, the software architecture 606 may include layers such as an operating system 602, libraries 620, applications 616 and a presentation layer 614. Operationally, the applications 616 and/or other components within the layers may invoke application programming interface (API) API calls 608 through the software stack and receive messages 612 in response to the API calls 608. The layers illustrated are representative in nature and not all software architectures have all layers. For example, some mobile or special purpose operating systems may not provide a frameworks/middleware 618, while others may provide such a layer. Other software architectures may include additional or different layers.

The operating system 602 may manage hardware resources and provide common services. The operating system 602 may include, for example, a kernel 622, services 624 and drivers 626. The kernel 622 may act as an abstraction layer between the hardware and the other software layers. For example, the kernel 622 may be responsible for memory management, processor management (e.g., scheduling), component management, networking, security settings, and so on. The services 624 may provide other common services for the other software layers. The drivers 626 are responsible for controlling or interfacing with the underlying hardware. For instance, the drivers 626 include display drivers, camera drivers, Bluetooth® drivers, flash memory drivers, serial communication drivers (e.g., Universal Serial Bus (USB) drivers), Wi-Fi® drivers, audio drivers, power management drivers, and so forth depending on the hardware configuration.

The libraries 620 provide a common infrastructure that is used by the applications 616 and/or other components and/or layers. The libraries 620 provide functionality that allows other software components to perform tasks in an easier fashion than to interface directly with the underlying operating system 602 functionality (e.g., kernel 622, services 624 and/or drivers 626). The libraries 620 may include system libraries 644 (e.g., C standard library) that may provide functions such as memory allocation functions, string manipulation functions, mathematical functions, and the like. In addition, the libraries 620 may include API libraries 646 such as media libraries (e.g., libraries to support presentation and manipulation of various media format such as MPREG4, H.264, MP3, AAC, AMR, JPG, PNG), graphics libraries (e.g., an OpenGL framework that may be used to render 2D and 3D in a graphic content on a display), database libraries (e.g., SQLite that may provide various relational database functions), web libraries (e.g., WebKit that may provide web browsing functionality), and the like. The libraries 620 may also include a wide variety of other libraries 648 to provide many other APIs to the applications 616 and other software components/modules.

The frameworks/middleware 618 (also sometimes referred to as middleware) provide a higher-level common infrastructure that may be used by the applications 616 and/or other software components/modules. For example, the frameworks/middleware 618 may provide various graphic user interface (GUI) functions, high-level resource management, high-level location services, and so forth. The frameworks/middleware 618 may provide a broad spectrum of other APIs that may be utilized by the applications 616 and/or other software components/modules, some of which may be specific to a particular operating system 602 or platform.

The applications 616 include built-in applications 638 and/or third-party applications 640. Examples of representative built-in applications 638 may include, but are not limited to, a contacts application, a browser application, a book reader application, a location application, a media application, a messaging application, and/or a game application. Third-party applications 640 may include an application developed using the ANDROID™ or IOS™ software development kit (SDK) by an entity other than the vendor of the particular platform, and may be mobile software running on a mobile operating system such as IOS™, ANDROID™, WINDOWS® Phone, or other mobile operating systems. The third-party applications 640 may invoke the API calls 608 provided by the mobile operating system (such as operating system 602) to facilitate functionality described herein.

The applications 616 may use built in operating system functions (e.g., kernel 622, services 624 and/or drivers 626), libraries 620, and frameworks/middleware 618 to create user interfaces to interact with users of the system. Alternatively, or additionally, in some systems interactions with a user may occur through a presentation layer, such as presentation layer 614. In these systems, the application/component “logic” can be separated from the aspects of the application/component that interact with a user.

FIG. 7 is a block diagram illustrating components (also referred to herein as “modules”) of a machine 700, according to some exemplary embodiments, able to read instructions from a machine-readable medium (e.g., a machine-readable storage medium) and perform any one or more of the methodologies discussed herein. Specifically, FIG. 7 shows a diagrammatic representation of the machine 700 in the example form of a computer system, within which instructions 710 (e.g., software, a program, an application, an applet, an app, or other executable code) for causing the machine 700 to perform any one or more of the methodologies discussed herein may be executed. As such, the instructions 710 may be used to implement modules or components described herein. The instructions 710 transform the general, non-programmed machine 700 into a particular machine 700 programmed to carry out the described and illustrated functions in the manner described. In alternative embodiments, the machine 700 operates as a standalone device or may be coupled (e.g., networked) to other machines. In a networked deployment, the machine 700 may operate in the capacity of a server machine or a client machine in a server-client network environment, or as a peer machine in a peer-to-peer (or distributed) network environment. The machine 700 may comprise, but not be limited to, a server computer, a client computer, a personal computer (PC), a tablet computer, a laptop computer, a netbook, a set-top box (STB), a personal digital assistant (PDA), an entertainment media system, a cellular telephone, a smart phone, a mobile device, a wearable device (e.g., a smart watch), a smart home device (e.g., a smart appliance), other smart devices, a web appliance, a network router, a network switch, a network bridge, or any machine capable of executing the instructions 710, sequentially or otherwise, that specify actions to be taken by machine 700. Further, while only a single machine 700 is illustrated, the term “machine” shall also be taken to include a collection of machines that individually or jointly execute the instructions 710 to perform any one or more of the methodologies discussed herein.

The machine 700 may include processors 704, memory memory/storage 706, and I/O components 718, which may be configured to communicate with each other such as via a bus 702. The memory/storage 706 may include a memory 714, such as a main memory, or other memory storage, and a storage unit 716, both accessible to the processors 704 such as via the bus 702. The storage unit 716 and memory 714 store the instructions 710 embodying any one or more of the methodologies or functions described herein. The instructions 710 may also reside, completely or partially, within the memory 714, within the storage unit 716, within at least one of the processors 704 (e.g., within the processor's cache memory), or any suitable combination thereof, during execution thereof by the machine 700. Accordingly, the memory 714, the storage unit 716, and the memory of processors 704 are examples of machine-readable media.

As used herein, the term “machine-readable medium,” “computer-readable medium,” or the like may refer to any component, device or other tangible media able to store instructions and data temporarily or permanently. Examples of such media may include, but is not limited to, random-access memory (RAM), read-only memory (ROM), buffer memory, flash memory, optical media, magnetic media, cache memory, other types of storage (e.g., Erasable Programmable Read-Only Memory (EEPROM)) and/or any suitable combination thereof. The term “machine-readable medium” should be taken to include a single medium or multiple media (e.g., a centralized or distributed database, or associated caches and servers) able to store instructions. The term “machine-readable medium” may also be taken to include any medium, or combination of multiple media, that is capable of storing instructions (e.g., code) for execution by a machine, such that the instructions, when executed by one or more processors of the machine, cause the machine to perform any one or more of the methodologies described herein. Accordingly, a “machine-readable medium” may refer to a single storage apparatus or device, as well as “cloud-based” storage systems or storage networks that include multiple storage apparatus or devices. The term “machine-readable medium” excludes signals per se.

The I/O components 718 may include a wide variety of components to provide a user interface for receiving input, providing output, producing output, transmitting information, exchanging information, capturing measurements, and so on. The specific I/O components 718 that are included in the user interface of a particular machine 700 will depend on the type of machine. For example, portable machines such as mobile phones will likely include a touch input device or other such input mechanisms, while a headless server machine will likely not include such a touch input device. It will be appreciated that the I/O components 718 may include many other components that are not shown in FIG. 7 . The I/O components 718 are grouped according to functionality merely for simplifying the following discussion and the grouping is in no way limiting. In various exemplary embodiments, the I/O components 718 may include output components 726 and input components 728. The output components 726 may include visual components (e.g., a display such as a plasma display panel (PDP), a light emitting diode (LED) display, a liquid crystal display (LCD), a projector, or a cathode ray tube (CRT)), acoustic components (e.g., speakers), haptic components (e.g., a vibratory motor, resistance mechanisms), other signal generators, and so forth. The input components 728 may include alphanumeric input components (e.g., a keyboard, a touch screen configured to receive alphanumeric input, a photo-optical keyboard, or other alphanumeric input components), point based input components (e.g., a mouse, a touchpad, a trackball, a joystick, a motion sensor, or other pointing instrument), tactile input components (e.g., a physical button, a touch screen that provides location and/or force of touches or touch gestures, or other tactile input components), audio input components (e.g., a microphone), and the like. The input components 728 may also include one or more image-capturing devices, such as a digital camera for generating digital images and/or video.

In further exemplary embodiments, the I/O components 718 may include biometric components 730, motion components 734, environmental environment components 736, or position components 738, as well as a wide array of other components. One or more of such components (or portions thereof) may collectively be referred to herein as a “sensor component” or “sensor” for collecting various data related to the machine 700, the environment of the machine 700, a user of the machine 700, or a combinations thereof.

For example, the biometric components 730 may include components to detect expressions (e.g., hand expressions, facial expressions, vocal expressions, body gestures, or eye tracking), measure biosignals (e.g., blood pressure, heart rate, body temperature, perspiration, or brain waves), identify a person (e.g., voice identification, retinal identification, facial identification, fingerprint identification, or electroencephalogram based identification), and the like. The motion components 734 may include acceleration sensor components (e.g., accelerometer), gravitation sensor components, velocity sensor components (e.g., speedometer), rotation sensor components (e.g., gyroscope), and so forth. The environment components 736 may include, for example, illumination sensor components (e.g., photometer), temperature sensor components (e.g., one or more thermometer that detect ambient temperature), humidity sensor components, pressure sensor components (e.g., barometer), acoustic sensor components (e.g., one or more microphones that detect background noise), proximity sensor components (e.g., infrared sensors that detect nearby objects), gas sensors (e.g., gas detection sensors to detection concentrations of hazardous gases for safety or to measure pollutants in the atmosphere), or other components that may provide indications, measurements, or signals corresponding to a surrounding physical environment. The position components 738 may include location sensor components (e.g., a Global Position system (GPS) receiver component), altitude sensor components (e.g., altimeters or barometers that detect air pressure from which altitude may be derived), orientation sensor components (e.g., magnetometers), and the like. For example, the location sensor component may provide location information associated with the system 700, such as the system's 700 GPS coordinates and/or information regarding a location the system 700 is at currently (e.g., the name of a restaurant or other business).

Communication may be implemented using a wide variety of technologies. The I/O components 718 may include communication components 740 operable to couple the machine 700 to a network 732 or devices 720 via coupling 722 and coupling 724 respectively. For example, the communication components 740 may include a network interface component or other suitable device to interface with the network 732. In further examples, communication components 740 may include wired communication components, wireless communication components, cellular communication components, Near Field Communication (NFC) components, Bluetooth® components (e.g., Bluetooth® Low Energy), Wi-Fi® components, and other communication components to provide communication via other modalities. The devices 720 may be another machine or any of a wide variety of peripheral devices (e.g., a peripheral device coupled via a Universal Serial Bus (USB)).

Moreover, the communication components 740 may detect identifiers or include components operable to detect identifiers. For example, the communication components 740 may include Radio Frequency Identification (RFID) tag reader components, NFC smart tag detection components, optical reader components (e.g., an optical sensor to detect one-dimensional bar codes such as Universal Product Code (UPC) bar code, multi-dimensional bar codes such as Quick Response (QR) code, Aztec code, Data Matrix, Dataglyph, MaxiCode, PDF417, Ultra Code, UCC RSS-2D bar code, and other optical codes), or acoustic detection components (e.g., microphones to identify tagged audio signals). In addition, a variety of information may be derived via the communication components 740, such as, location via Internet Protocol (IP) geo-location, location via Wi-Fi® signal triangulation, location via detecting a NFC beacon signal that may indicate a particular location, and so forth.

Where a phrase similar to “at least one of A, B, or C,” “at least one of A, B, and C,” “one or more A, B, or C,” or “one or more of A, B, and C” is used, it is intended that the phrase be interpreted to mean that A alone may be present in an embodiment, B alone may be present in an embodiment, C alone may be present in an embodiment, or that any combination of the elements A, B and C may be present in a single embodiment; for example, A and B, A and C, B and C, or A and B and C.

A portion of the disclosure of this patent document contains material that is subject to copyright protection. The copyright owner has no objection to the facsimile reproduction by anyone of the patent document or the patent disclosure, as it appears in the Patent and Trademark Office patent files or records, but otherwise reserves all copyright rights whatsoever. The following notice applies to the software and data as described below and in the drawings that form a part of this document: Copyright 2016, SNAPCHAT, INC. 2016, All Rights Reserved.

Changes and modifications may be made to the disclosed embodiments without departing from the scope of the present disclosure. These and other changes or modifications are intended to be included within the scope of the present disclosure, as expressed in the following claims. 

What is claimed is:
 1. A system comprising: a processor; and memory storing instructions that, when executed by the processor, cause the processor to perform operations comprising: receiving a media content item; generating a plurality of media overlays; generating an avatar of a user, wherein the avatar of the user is a visual representation of the user, wherein an appearance of the avatar of the user is generated to reflect a theme included in themes of the plurality of media overlays, wherein the appearance of the avatar of the user is different in each of the media overlays when the avatar is incorporated into each of the media overlays; receiving a selection of a first selectable item that corresponds to a first media overlay included in the plurality of media overlays; in response to receiving the selection, generating a modified media content item by incorporating the first media overlay including the avatar of the user with the media content item, wherein incorporating the first media overlay with the media content item comprises overlaying the first media overlay on the media content item; and causing the modified media content item to be displayed on a display screen.
 2. The system of claim 1, wherein the media content item is an image or a video.
 3. The system of claim 1, wherein the system further comprises: an image capturing device, and wherein the media content item is received from the image capturing device.
 4. The system of claim 1, wherein the media content item is received from a computing device over a network.
 5. The system of claim 1, wherein generating the plurality of media overlays is further based on at least one of: location information, an event, a time of day, or a date, and wherein the appearance of the avatar of the user in each of the media overlays is modified based on at least one of the location information, the event, the time of day, or the date.
 6. The system of claim 5, wherein generating the plurality of media overlays based on the time of day includes identifying time information or time zone information from a clock operating on the system.
 7. The system of claim 5, wherein generating the plurality of media overlays based on the location information includes identifying a location from a location sensor coupled to the processor.
 8. The system of claim 1, wherein generating the plurality of media overlays includes modifying a setting of the media overlay or modifying the avatar of the user.
 9. The system of claim 1, wherein generating the plurality of media overlays includes providing access to the media overlays by the user for a predetermined time period.
 10. The system of claim 1, wherein the operations further comprise: retrieving sensor information from a sensor component coupled with the processor, and wherein generating the plurality of media overlays is further based on the sensor information.
 11. The system of claim 10, wherein the sensor component includes at least one of: a temperature sensor, a velocity sensor, an acceleration sensor, and an altitude sensor.
 12. The system of claim 1, wherein the operations further comprise: receiving a selection of a second selectable item that corresponds to a second media overlay included in the plurality of media overlays, and wherein generating the modified media content item includes overlaying the first media overlay and the second media overlay on the media content item.
 13. The system of claim 1, wherein the operations further comprise: in response to the selection of the first selectable item corresponding to the first media overlay, removing a second media overlay from the plurality of media overlays displayed to the user via the display screen of the user interface.
 14. The system of claim 1, wherein the operations further comprise: storing a history of media content items with applied media overlays in a database in communication with the system.
 15. The system of claim 14, wherein the operations further comprise: retrieving the history of media content items with applied media overlays from the database; and causing the history of media content items to be displayed on the display screen of the user interface.
 16. The system of claim 15, wherein the first media content item displayed in the history of media content items has a media content overlay with a previous version of the user's avatar, and wherein displaying the history of media content items includes displaying the first media content item with a current version of the user's avatar.
 17. The system of claim 1, wherein the operations further comprise: generating text for each of the plurality of media overlays, wherein each of the media overlays includes the generated text.
 18. The system of claim 17, wherein generating the text for each of the media overlays includes: identifying a location based on information from a location sensor coupled to the processor; identifying a language associated with the location; and generating the text in the media overlays in the identified language.
 19. The system of claim 1, wherein generating the media overlay includes: transmitting, to a server over a network, a request for the plurality of media overlays, the request including avatar characteristics associated with the user; and receiving, from the server over the network, the plurality of media overlays each comprising the avatar of the user.
 20. A computer-implemented method comprising: receiving, by a processor, a media content item; generating, by the processor, a plurality of media overlays; generating, by the processor, an avatar of the user, wherein the avatar of the user is a visual representation of the user, wherein an appearance of the avatar of the user is generated to reflect a theme included in themes of the plurality of media overlays, wherein the appearance of the avatar of the user is different in each of the media overlays when the avatar is incorporated into each of the media overlays; receiving a selection, by the processor, of a first selectable item that corresponds to a first media overlay included in the plurality of media overlays; in response to receiving the selection, generating, by the processor, a modified media content item by incorporating the first media overlay including the avatar of the user with the media content item, wherein incorporating the first media overlay with the media content item comprises overlaying the first media overlay on the media content item; and causing, by the processor, the modified media content item to be displayed on a display screen of a user interface.
 21. A non-transitory computer-readable medium storing instructions that, when executed by a processor, cause the processor to perform operations comprising: receiving a media content item; generating a plurality of media overlays; generating an avatar of a user, wherein the avatar of the user is a visual representation of the user, wherein an appearance of the avatar of the user is generated to reflect a theme included in themes of the plurality of media overlays, wherein the appearance of the avatar of the user is different in each of the media overlays when the avatar is incorporated into each of the media overlays; receiving a selection of a first selectable item that corresponds to a first media overlay included in the plurality of media overlays; in response to receiving the selection, generating a modified media content item by incorporating the first media overlay including the avatar of the user with the media content item, wherein incorporating the first media overlay with the media content item comprises overlaying the first media overlay on the media content item; and causing the modified media content item to be displayed on a display screen of a user interface. 